Pulse oximetry system

ABSTRACT

Systems, methods, and devices for intercommunication between a medical sensor and an electronic patient monitor are provided. For example, one embodiment of a system for communicably coupling a medical sensor to an electronic patient monitor may include a sensor-side communication connector and a monitor-side communication connector. The sensor-side communication connector may be capable of receiving a raw physiological measurement signal from the medical sensor, and the monitor-side communication connector may be capable of providing a digital physiological measurement signal based at least in part on the raw physiological measurement signal to the electronic patient monitor via a data link.

BACKGROUND

The presently disclosed subject matter relates generally to communicating data from a medical sensor to an electronic patient monitor and, more particularly, to communicating physiological measurements from data or instructions for obtaining physiological measurements from data to an electronic patient monitor.

This section is intended to introduce the reader to various aspects of art that may be related to various aspects of the present disclosure, which are described and/or claimed below. This discussion is believed to be helpful in providing the reader with background information to facilitate a better understanding of the various aspects of the present disclosure. Accordingly, it should be understood that these statements are to be read in this light, and not as admissions of prior art.

Electronic patient monitors may be commonly used to monitor patient parameters such as ECG, pulse oximetry, blood pressure, and/or body temperature, among other things. Multi-parameter electronic patient monitors may be expensive electronic patient monitor units that display such patient parameters from a number of supported sensor types. To accommodate sensors from a variety of manufacturers, such monitors may be designed to employ a proprietary connector for each sensor type. The sensors may be attached to the monitor via the connector through a patient cable. The patient monitor may contain a dedicated circuit that acquires data from the sensor and may include a special module that specializes in the type of sensor. For example, a multi-parameter monitor may contain an Original Equipment Manufacturer (OEM) module to determine physiological measurements from a raw measurement. By way of example, within a single electronic patient monitor, a first OEM module from a first manufacturer may receive a raw signal from a photoplethysmographic sensor, determining pulse rate and/or oxygen saturation based on the raw signal. A second OEM module from a different manufacturer may receive a raw signal from a blood pressure cuff, determining blood pressure based on the raw signal.

The OEM modules in a multi-parameter monitor may be very difficult to upgrade, as the monitor may be disassembled before the OEM module is replaced. Thus, it may be unlikely for major upgrades to a patient monitor to occur once the patient monitor has been delivered to a medical facility. Accordingly, new developments, such as improved algorithms for obtaining physiological measurements from sensor data, may not easily be included in existing patient monitors. While some upgrades involve only firmware changes, the difficulty in upgrading is especially relevant when hardware or connector changes are required. In practice, expensive monitors are seldom upgraded in the field. Typically, another device is placed next to the old monitor, resulting in cluttered hospital environments and multiple displays for the caregivers to read. It may also be difficult to base alarm decisions on multiple monitors since they typically do not communicate with each other

SUMMARY

Certain aspects commensurate in scope with the originally claimed embodiments are set forth below. It should be understood that these aspects are presented merely to provide the reader with a brief summary of certain forms the embodiments might take and that these aspects are not intended to limit the scope of the presently disclosed subject matter. Indeed, the embodiments may encompass a variety of aspects that may not be set forth below.

Present embodiments relate to systems, methods, and devices for intercommunicating medical sensors and electronic patient monitors. For example, one embodiment of a system for communicably coupling a medical sensor to an electronic patient monitor may include a sensor-side communication connector and a monitor-side communication connector. The sensor-side communication connector may be capable of receiving a raw physiological measurement signal from the medical sensor, and the monitor-side communication connector may be capable of providing a digital physiological measurement signal based at least in part on the raw physiological measurement signal to the electronic patient monitor via a data link.

BRIEF DESCRIPTION OF THE DRAWINGS

Advantages of the presently disclosed subject matter may become apparent upon reading the following detailed description and upon reference to the drawings in which:

FIG. 1 is a schematic diagram of a system having instructions for sensor processing in sensor-monitor communication circuitry, in accordance with an embodiment;

FIG. 2 is a block diagram of the system of FIG. 1, in accordance with an embodiment;

FIG. 3 is a more detailed block diagram of the system of FIG. 1, in accordance with an embodiment;

FIG. 4 is a block diagram of a cable connection to a medical sensor, in accordance with an embodiment;

FIG. 5 is a block diagram of a data link to a patient monitor, in accordance with an embodiment;

FIG. 6 is a flowchart describing an embodiment of a method for processing sensor data in a patient cable;

FIG. 7 is a block diagram of an alternative system of FIG. 1, in accordance with an embodiment;

FIG. 8 is a flowchart of an embodiment of a method for processing sensor data in a patient monitor based on instructions from a patient cable,;

FIG. 9 is a block diagram of an alternative system for providing sensor data to a patient monitor, in accordance with an embodiment;

FIG. 10 is a block diagram describing the system of FIG. 9 in greater detail, in accordance with an embodiment;

FIG. 11 is a flowchart describing an embodiment of a method for upgrading firmware in a patient cable; and

FIGS. 12-17 are flowcharts describing embodiments of methods for determining a protocol for communication between a patient cable and a patient monitor.

DETAILED DESCRIPTION

One or more specific embodiments of the present disclosure will be described Below. In an effort to provide a concise description of these embodiments, not all features of an actual implementation are described in the specification. It should be appreciated that in the development of any such actual implementation, as in any engineering or design project, numerous implementation-specific decisions must be made to achieve the developers' specific goals, such as compliance with system-related and business-related constraints, which may vary from one implementation to another. Moreover, it should be appreciated that such a development effort might be complex and time consuming, but would nevertheless be a routine undertaking of design, fabrication, and manufacture for those of ordinary skill having the benefit of this disclosure.

Present embodiments may apply to a variety of medical sensors, including photoplethysmographic sensors, temperature sensors, respiration bands, blood pressure sensors, electrocardiogram (ECG) sensors, electroencephalogram (EEG) sensors, pulse transit time sensors, and so forth. Such sensors may communicate with an electronic patient monitor using intercommunication circuitry such as a patient cable or a wireless connection. According to embodiments disclosed herein, sensor-monitor intercommunication circuitry may include instructions for obtaining physiological measurements from raw measurements. As such, an electronic patient monitor may receive a signal over a data link using a proprietary or universal protocol from such intercommunication circuitry, despite that a specific OEM board may not necessarily be installed within the receiving monitor. For example, the patient cable may transmit messages indicating the physiological measurements or provide instructions for obtaining the physiological measurements to the monitor using a protocol that may be proprietary to the monitor.

As used in the present disclosure, “instructions” that may be used for obtaining physiological measurements may refer to any information that enables the monitor to determine physiological characteristics of a patient from data collected by a medical sensor. Such instructions may include executable code (e.g., software) written specifically for the host processor of the monitor, or written to support any suitable processor type. The instructions could include a protocol whereby the processor is instructed to load such executable code and/or data memory to an absolute or relative address in the processor's memory. Additionally or alternatively, the instructions could include a high level script, which may be a proprietary format or an open format (e.g., Sun's JAVA language or Perl/Unix shell scripts), which is not processor-specific and which may instruct the processor to perform certain operations on the data.

With the foregoing in mind, FIG. 1 illustrates a perspective view of an embodiment of a sensor-monitor interconnection system 10 for communicably coupling an electronic patient monitor 12 to a medical sensor 14. Although the embodiment of the system 10 illustrated in FIG. 1 relates to photoplethysmography, the system 10 may be configured to obtain a variety of physiological measurements using a suitable medical sensor. For example, the system 10 may, additionally or alternatively, be configured to obtain a respiration rate, a patient temperature, an ECG, an EEG, a blood pressure, and/or a pulse transit time, and so forth.

The patient monitor 12 may communicate with the medical sensor 14 via a short analog cable 18 coupled to a sensor-monitor intercommunication cable 20. The patient monitor 12 may include a display 16, a memory, and various monitoring and control features. In certain embodiments, the patient monitor 12 may include a processor configured to receive software instructions from the sensor-monitor intercommunication cable 20. The software instructions may be employed by the processor in the patient monitor 12 to obtain physiological measurements, such as pulse rate or blood oxygen saturation, from raw photoplethysmographic data or other raw data that has been digitized within the sensor-monitor intercommunication cable 20. In other embodiments, the patient monitor 12 may not include a processor with such capabilities, but may rather be configured to display physiological measurements, such as pulse rate or blood oxygen saturation, that have been determined within the sensor-monitor intercommunication cable 20. For example, when the system 10 is configured for photoplethysmography, the sensor-monitor intercommunication cable 20 may include software instructions and/or capabilities for performing pulse oximetry measurements, calculations, and control algorithms, based on the sensor data received from the medical sensor 14.

In the presently illustrated embodiment of the system 10, the medical sensor 14 is a photoplethysmographic sensor. As should be appreciated, however, the sensor 14 may be a photoplethysmographic sensor, a temperature sensor, a respiration band, a blood pressure sensor, an arrhythmia sensor, a pulse transit time sensor, or any other suitable medical sensor. As noted above, the sensor 14 may include the short analog cable 18. The short analog cable 18 may include a sensor connector 22 that joins to a sensor-side cable connector 24 of the sensor-monitor intercommunication cable 20. The analog cable 18 may be of a sufficiently short length to prevent excessive interference before reaching the sensor-monitor intercommunication cable 20. The sensor-monitor intercommunication cable 20 may include the sensor-side cable connector 24, a monitor protocol selection button or switch 25, intercommunication cabling 26, and a monitor-side cable connector 28. The monitor-side cable connector 28 may join to a monitor connector 30 with a data communication link, such as a serial peripheral interface (SPI), a universal serial bus (USB) interface, a universal asynchronous receiver/transmitter (UART) interface, a Two Wire Interface (TWI such as I2C, or an RS232 interface, or any other suitable communication link.

As described in greater detail below, the sensor-monitor intercommunication cable 20 may communicate with the monitor 12 using a protocol understandable by the monitor 12. Such protocols may include, for example, the Standard Host Interface Protocol (SHIP) or the Phillips Interface Protocol (PIP). The sensor-monitor intercommunication cable 20 may be preprogrammed to communicate using the protocol or may automatically select the particular protocol from among a variety of preprogrammed protocols, as described below with reference to FIGS. 12 and 13. Additionally or alternatively, a practitioner may manually set the protocol by pressing the button or switch 25 or selecting a setting on the button or switch 25. Thereafter, the sensor-monitor intercommunication cable 20 may communicate with the electronic patient monitor 12 and may not need to be specific to particular vendors or to particular sensors. Additionally or alternatively, the sensor-monitor intercommunication cable 20 may automatically negotiate a mutually supported protocol with the electronic patient monitor 12 or use other techniques to determine such a protocol, as generally described below with reference to FIGS. 12-17.

A sensor assembly or body 32 of the wireless medical sensor 14 may attach to patient tissue (e.g., a patient's finger, ear, forehead, or toe). In the illustrated embodiment, the sensor assembly 32 is configured to attach to a finger. The medical sensor 14, illustrated in the present embodiment as a photoplethysmographic sensor, may include an emitter 34 and a detector 36. When attached to pulsatile tissue of a patient 38, the emitter 34 may transmit light at certain wavelengths into the tissue and the detector 36 may receive the light after it has passed through or is reflected by the tissue. The amount of light that passes through the tissue and other characteristics of light waves may vary in accordance with the changing amount of certain blood constituents in the tissue and the related light absorption and/or scattering. For example, the emitter 34 may emit light from two or more LEDs or other suitable light sources into the pulsatile tissue. The reflected or transmitted light may be detected with the detector 36, such as a photodiode or photo-detector, after the light has passed through or has been reflected by the pulsatile tissue.

FIG. 2 is a simplified block diagram of the system 10 of FIG. 1. As illustrated in FIG. 2, the sensor 14 may connect to the patient monitor 12 by way of the sensor-monitor intercommunication cable 20. In particular, the sensor connector 22 of the analog cable 18 may connect to the sensor-side cable connector 24 of the sensor-monitor intercommunication cable 20. The sensor-side cable connector 24 may receive analog data from the medical sensor 14, digitize the data, and transmit the digitized data to the monitor-side cable connector 28 via the digital cable 26. One embodiment of the digital cable 26 may include minimal interconnecting cabling, which may include, for example, two power subcables and digital communication subcabling, as described below with reference to FIG. 4. It should be appreciated that the digital cable 26 may employ any suitable power cabling structures and/or techniques, and should not be understood to be limited to two power subcables.

In alternative embodiments, the sensor-side cable connector 24 may transmit the received analog data to the monitor-side cable connector 28 without first digitizing the data. With such alternative embodiments, the monitor-side cable connector 28 may instead digitize the analog data. If the sensor-side cable connector 24 does not first digitize the analog data before transmitting the data to the monitor-side cable connector 28, additional cabling and shielding may be employed to prevent attenuation and/or interference.

The monitor-side cable connector 28 may process the digitized data to obtain a physiological measurement, transmitting the determined physiological measurement to the patient monitor 12 via the monitor connector 30. Alternatively, the monitor-side cable connector 28 may transmit software instructions for obtaining the physiological measurements from the digitized data to the monitor 12. Thereafter, the monitor-side cable connector 28 may transmit the digitized data to the monitor 12 via the monitor connector 30, which may process the digitized data according to the received software instructions to obtain physiological measurements.

As described below, the monitor-side cable connector 28 may communicate with the monitor 12 via the monitor connector 30 using any suitable protocol. For example, the monitor 12 may only communicate via a single protocol, such as Phillips Interface Protocol (PIP), and the monitor-side cable connector 28 may communicate using the PIP protocol after automatically determining that messages sent to the monitor 12 be transmitted using the PIP protocol, as described below with reference to FIGS. 12-13, or after being manually set by a practitioner via the button or switch 25.

As described further below, the monitor-side cable connector 28 may autodetect the protocol by, for example, sending a command in a given protocol and waiting for a valid response. If no valid response is returned by the monitor 12 within a given time, and the monitor-side cable connector 28 may continue trying other protocols until a message type is found to which the monitor 12 responds. After such an initial negotiation, the monitor-side cable connector 28 may stay in the negotiated protocol until power off. Additionally or alternatively, the monitor-side cable connector 28 may store the negotiated protocol in its non-volatile memory 62 and may remember the setting at next power up (reverting to negotiations only if the saved protocol fails). Additionally or alternatively, the monitor 12 may negotiate with the monitor-side cable connector 28. In some embodiments, the monitor 12 may identify its protocol at startup by sending a message type agreed on by several or all manufacturers of patient monitors. In some embodiments, certain connector pins may be connected to power or ground, or to specific resistors or voltages, through which the monitor-side cable connector 28 may identify the type of the monitor 12. Also, in some embodiments, the protocol may be determined during a USB device enumeration process.

The monitor connector 30 attached to the monitor 12 may represent a communication data link capable of communicating via one or more protocols. As noted above, the monitor connector 30 may include a serial peripheral interface (SPI), a universal serial bus (USB) interface, a universal asynchronous receiver/transmitter (UART) interface, a Two Wire Interface (TWI) such as I2C, or an RS232 interface, or any other suitable communication link. One embodiment of the pinout of the monitor connector 30 is described in greater detail below with reference FIG. 5.

FIG. 3 is a more detailed block diagram of the system 10. By way of example, embodiments of the system 10 may be implemented with any suitable medical sensor and patient monitor, such as those available from Nellcor Puritan Bennett LLC. The system 10 may include the patient monitor 12, the sensor 14, and the sensor-monitor intercommunication cable 20, which may be configured to obtain, for example, a photoplethysmographic signal from patient tissue at certain predetermined wavelengths. The medical sensor 14 may be communicatively connected to the patient monitor 12 via the sensor-monitor intercommunication cable 20. When the system 10 is operating, light from the emitter 34, which may include one or more light emitting diodes (LEDs) of certain wavelengths, may pass into the patient 38 and be scattered and detected by the detector 36.

Specifically, the sensor 14 may be controlled by the signals from the sensor-side cable connector 24. A digital communication interface 40 may receive control signals from the monitor-side cable connection 28, which may control the manner in which sensor interface circuitry 42 controls the sensor 14. The sensor interface circuitry 42 may control the sensor 14 using any suitable pulse oximetry technique. In some embodiments, a time processing unit (TPU) may provide timing control signals to light drive circuitry. Such light drive circuitry may drive the emitter 34, controlling when the emitter 34 is illuminated, and if multiple light sources are used, the multiplexed timing for the different light sources. The sensor interface circuitry 42 may also receive signals from the detector 36. The signals from the detector 36 may represent raw analog data, which may be digitized by the sensor interface circuitry 42. In some embodiments, the sensor interface circuitry 42 may include, for example, an amplifier, a filter, and an analog to digital (A/D) converter circuit. The sensor interface circuitry 42 may sample these signals at the proper time, depending upon which of multiple light sources is illuminated, if multiple light sources are used. The sampled signals represent digitized raw data that may be, for example, a raw 16-bit digital stream of photoplethysmographic data sampled at 100 Hz.

In an embodiment, the sensor 14 may also contain an encoder 48 that provides signals indicative of the wavelength of one or more light sources of the emitter 34, which may allow for selection of appropriate calibration coefficients for calculating a physiological parameter such as blood oxygen saturation. The encoder 48 may, for instance, be a coded resistor, EEPROM or other coding devices (such as a capacitor, inductor, PROM, RFID, parallel resonant circuits, or a colorimetric indicator) that may provide a signal related to the characteristics of the medical sensor 14 that may indicate appropriate calibration characteristics for the photoplethysmographic sensor 14. Further, the encoder 48 may include encryption coding that prevents a disposable part of the photoplethysmographic sensor 14 from being recognized by a processor 38 that is not able to decode the encryption. For example, a detector/decoder 50 may be required to translate information from the encoder 48 before it can be properly processed to obtain physiological measurements from the digitized raw data output by the sensor interface circuitry 42.

Digital data from the detector/decoder 50 and/or the sensor interface circuitry 42 may be sent to the digital communication interface 40. Additionally, if present, the button or switch 25 may provide digital information to the digital communication interface 40 indicating the particular protocol with which the sensor-monitor intercommunication cable 20 should use to communicate with the electronic patient monitor 12. The digital communication interface 40 may coordinate the transmission of the digital data to the monitor-side cable connector 28. The digital data may be transmitted over the digital cable 26 and received by another digital communication interface 52 using any suitable protocol. For example, the digital communication interfaces 40 and 52 may communicate using, for example, a serial peripheral interface (SPI), a universal serial bus (USB) interface, a universal asynchronous receiver/transmitter (UART) interface, a Two Wire Interface (TWI) such as I2C, or an RS232 interface. The digital data may be provided to a bus 54 connected to a microprocessor 56.

In various embodiments, based at least in part upon the value of the received digitized raw data corresponding to the light received by detector 36, the microprocessor 56 may calculate a physiological parameter of interest using various algorithms. These algorithms may utilize coefficients, which may be empirically determined, corresponding to, for example, the wavelengths of light used. The algorithms may store interim values and other digital data in RAM 58. The algorithms and other software instructions for obtaining a physiological measurement based on the digitized data may be stored in ROM 60 or nonvolatile storage 62, which may include, for example, Flash memory. In a two-wavelength system, the particular set of coefficients chosen for any pair of wavelength spectra may be determined by the value indicated by the encoder 48 corresponding to a particular light source provided by the emitter 34. For example, the first wavelength may be a wavelength that is highly sensitive to small quantities of deoxyhemoglobin in blood, and the second wavelength may be a complimentary wavelength. Specifically, for example, such wavelengths may be produced by orange, red, infrared, green, and/or yellow LEDs. Different wavelengths may be selected based on instructions from the patient monitor 12, preferences stored in a nonvolatile storage 62. Such instructions or preferences may be selected at the patient monitor 12 by a switch on the patient monitor 12, a keyboard, or a port providing instructions from a remote host computer. Other software or instructions for carrying out the techniques described herein may also be stored on the nonvolatile memory 62, or may be stored on the ROM 60. The physiological measurements determined in the sensor-monitor intercommunication cable 20 may be encoded in a first protocol, which may or may not be proprietary to the sensor-monitor intercommunication cable 20. As described below, the physiological measurements may be translated from the first protocol into a second protocol understandable to the monitor 12, if the monitor 12 is not capable of understanding the first protocol.

After determining physiological measurements based on the received digitized raw data, the microprocessor 56 may communicate with the monitor 12 via a cable-monitor interface 64. The cable-monitor interface 64 may transmit these physiological measurements and/or the digitized raw data to the monitor 12 via the monitor connector 30. The sensor-monitor intercommunication cable 20 may communicate using messages in a protocol understandable by the electronic patient monitor 12. The protocol may be indicated by a selection made by the button or switch 25, or may be determined automatically by the sensor-monitor intercommunication cable 20, as described below with reference to FIGS. 12 and 13. In this way, the sensor-monitor intercommunication cable 20 may not need to be specific to a manufacturer or vendor.

It should be appreciated that the configuration of the sensor-monitor intercommunication cable 20 illustrated in FIG. 3 may vary. For example, certain circuitry of the sensor-side cable connector 24 may be incorporated into the monitor-side cable connector 28. If the sensor interface circuitry 42 is incorporated into the monitor-side cable connector 28, the cable 26 may transmit analog signals rather than digital signals, and additional shielding may be used to reduce attenuation and/or interference. Similarly, certain circuitry of the monitor-side cable connector 28 may be incorporated into the sensor-side cable connector 24, such as the microprocessor 56. If the microprocessor 56 is incorporated into the sensor-side cable connector 24, the sensor-side cable connector may have the capability to determine physiological measurements from the digitized data, which may be transmitted over the digital cable 26. In certain other embodiments, all or part of the circuitry of the sensor-monitor intercommunication cable 20 may be incorporated into the medical sensor 14. However, if the medical sensor 14 is a replaceable sensor, incorporating such circuitry into the sensor 14 may be costly. Moreover, as described below with reference to FIGS. 9 and 10, circuitry with the capabilities described above may be incorporated into other intercommunication links between the sensor 14 and the electronic patient monitor. For example, the circuitry may be incorporated into a separable cable connector or dongle, or into wireless adapters for joining the medical sensor 14 and the patient monitor 12.

FIG. 4 illustrates an exemplary configuration of an embodiment of the digital cable 26 between the sensor-side cable connector 24 and the monitor-side cable connector 28. Specifically, the digital cable 26 may include power, such as a 5V supply 66 in one particular embodiment, a ground line 68, and one or more digital communication lines 70. The digital communication lines may employ any suitable protocol for intercommunication of digital data between the sensor-side cable connector 24 and the monitor-side cable connector 28. For example, as noted above, such protocols may include serial peripheral interface (SPI), universal serial bus (USB), universal asynchronous receiver/transmitter (UART), a Two Wire Interface (TWI) such as I2C, or RS232 protocols.

The digital cable 26 may carry signals over the longest distance of the sensor-monitor intercommunication cable 20. By transmitting digital signals rather than analog, the digital cable 26 may not require as much shielding as a cable for transmitting an analog signal. Though some cable shielding may be employed to reduce electromagnetic emissions from the cable 26, the digitized signals may be much less likely to be corrupted by electromagnetic noise than low amplitude sensor outputs. Moreover, digital errors over the digital cable 26 may be detected, corrected, or may trigger data re-transmission in communications between the sensor-side cable connector 24 and the monitor-side cable connector 28.

FIG. S illustrates an exemplary configuration of an embodiment of the pinout interconnections between the cable-monitor interface 64 of the monitor-side cable connector 28 and the monitor connector 30. The pinout configuration may employ any suitable protocol for intercommunication of digital data between the cable-monitor interface 64 and the monitor connector 30. For example, as noted above, such protocols may include serial peripheral interface (SPI), universal serial bus (USB), universal asynchronous receiver/transmitter (UART), a Two Wire Interface (TWI) such as I2C, or RS232 protocols.

In the instant exemplary configuration, the pinout configuration may include a 5V line 72, a ground line 74, and various signal interfaces corresponding to serial peripheral interface (SPI) pins. These may include a synchronous clock (SCK) 76 pin, a master input/slave output (MISO) 78 pin, a master output/slave input (MOSI) 80 pin, and a chip select (CS) pin 82. The SCK 76 may provide a serial clock input from the patient monitor 12 to the sensor-monitor intercommunication cable 20. The MISO 78 may transmit synchronous serial data, such as physiological measurements determined in the monitor-side cable connector 28, from the sensor-monitor intercommunication cable 20 to the patient monitor 12. The MOSI 80 may transmit synchronous serial data, such as sensor control signals, from the patient monitor 12 to the sensor-monitor intercommunication cable 20. The patient monitor 12 may use the CS 82 to elect to communicate with the sensor-monitor intercommunication cable 20. To reduce pin count, the CS signal 82 may be omitted from the connector and tied to ground (active low) at the slave side if there is only one master and one slave on the bus. The cable may be designed such that either the monitor 12 or the sensor-monitor intercommunication cable 20 is the SPI bus master. In this way, the configuration illustrated in FIG. 5 may enable the patient monitor 12 to control a number of different sensors 14 coupled via similar SPI configurations and sensor-monitor intercommunication cables 20.

FIG. 6 is a flowchart 84 describing an embodiment of a method for communicably coupling the medical sensor 14 to the patient monitor 12 via the sensor-monitor intercommunication cable 20. In particular, the embodiment of the method of the flowchart 84 contemplates a sensor-monitor intercommunication cable 20 that includes the microprocessor 56, as well as appropriate software instructions stored within the ROM 60 or the nonvolatile memory 62. Because the sensor-monitor intercommunication cable 20 includes the processor 56, the patient monitor 12 need not include a processor capable of extracting physiological measurements based on data from the sensor 14. Rather, the patient monitor 12 may require only the capability to display data received from the sensor-monitor intercommunication cable 20. The flowchart 84 may be carried out using the embodiment of FIG. 3, as well as embodiments with similar capabilities, such as those described below with reference to FIGS. 9 and 10.

In a first step 86, the sensor-monitor intercommunication cable 20 may obtain analog raw data from the sensor 14. Depending on the medical sensor 14, such analog data may include, for example, photoplethysmographic data, temperature data, respiration data, blood pressure data, arrhythmia data, ECG data, pulse transit time data, and so forth. By way of example, the analog raw data may be received by the sensor-side cable connector 24. In step 88, the raw analog data may be digitized by the sensor-monitor intercommunication cable 20 to obtain digitized raw data. If the analog raw data is a photoplethysmographic signal, the digitized raw data may be, for example, a raw 16-bit digital stream of photoplethysmographic data sampled at 100 Hz. Such digitization may take place via the sensor interface circuitry 42 in the sensor-side cable connector 24.

In step 90, the sensor-monitor intercommunication cable 20 may convert the digitized raw data into physiological measurements. By way of example, if the digitized raw data is photoplethysmographic data, the physiological measurements may include pulse rate, blood oxygen saturation, and/or total hemoglobin measurements. The physiological measurements may be obtained by the processing the digitized raw data using the microprocessor 56, according to instructions stored in the ROM 60 or nonvolatile memory 62. These physiological measurements may be transmitted to the patient monitor 12 in step 92, and displayed on the patient monitor 12 in step 94. The sensor-monitor intercommunication cable 20 may communicate with the electronic patient monitor 12 using messages of a protocol understandable by the electronic patient monitor 12. The protocol may be indicated by a selection made by the button or switch 25, or may be determined automatically by the sensor-monitor intercommunication cable 20, as described below with reference to FIGS. 12 and 13. In this way, the sensor-monitor intercommunication cable 20 may not need to be specific to a manufacturer or vendor.

In some embodiments, the physiological measurements obtained in step 90 may be used to determine alarm status. For example, the patient monitor 12 may indicate alarm limits for certain detectable physiological parameters to the sensor-monitor intercommunication cable 20. If the physiological measurements obtained in step 90 exceed the alarm limits (e.g., if heart rate or SpO₂ exceed a predetermined range), the sensor-monitor intercommunication cable 20 may respond accordingly. For example, in step 92, the sensor-monitor intercommunication cable 20 may transmit such an alarm to the patient monitor 12 in step 92.

As noted above, the circuitry and capabilities of the sensor-monitor intercommunication cable 20 may vary. FIG. 7 illustrates an alternative embodiment of the system 10, in which the sensor-monitor intercommunication cable 20 is capable of digitizing sensor 14 data, but lacks the ability to process the digitized data into physiological measurements on its own. In particular, the embodiment of the system 10 illustrated in FIG. 7 may be substantially identical to the embodiment of the system 10 illustrated in FIG. 3, except that the monitor-side cable connector 28 may lack the microprocessor 56 and/or RAM 58. When used with a patient monitor 12 having a suitable processor, however, the sensor-monitor intercommunication cable 20 may provide the patient monitor 12 with software instructions for obtaining such physiological measurements. Such instructions may be stored, for example, in the ROM 60 or the nonvolatile memory 62. After receiving the software instructions from the sensor-monitor intercommunication cable 20, the patient monitor 12 may thereafter obtain the physiological measurements based on digitized raw data received from the sensor-monitor intercommunication cable 20.

A flowchart 96, illustrated in FIG. 8, describes an embodiment of a method for processing medical sensor 14 data in the patient monitor 12 using software instructions provided by the sensor-monitor intercommunication cable 20. The embodiment of the method of the flowchart 96 may be performed using either of the embodiments of the sensor-monitor intercommunication cable 20 described in FIG. 3 or FIG. 7, as well as the embodiments of similar circuitry with similar capabilities described below with reference to FIGS. 9 and 10. The electronic patient monitor 12 should include a processor capable of obtaining physiological measurements from digitized raw data, when provided the appropriate software.

In a first step 98, the sensor-monitor intercommunication cable 20 may send software instructions for obtaining physiological measurements from raw data, which may be in the form of firmware or a driver, to the electronic patient monitor 12. Step 98 may take place, for example, when the electronic patient monitor boots up from an SPI flash memory device, or boot memory, located in the sensor-monitor intercommunication cable 20. In step 100, the sensor-monitor intercommunication cable 20 may receive analog raw data from the sensor 14, in generally the same manner as described with reference to step 86 of the flowchart 84. In step 102, the raw analog data may be digitized by the sensor-monitor intercommunication cable 20 to obtain digitized raw data, in generally the same manner as described with reference to step 88 of the flowchart 84.

In step 104, the digitized raw data may be transmitted to the electronic patient monitor 12 in a particular protocol understandable to the monitor 12. A practitioner may select the protocol via the button or switch 25, the sensor-monitor intercommunication cable 20 may be preprogrammed to communicate using the protocol, or the sensor-monitor intercommunication cable 20 may automatically select the proper protocol, as described below with reference to FIGS. 12 and 13. Using the firmware or driver received in step 98, in step 106, the monitor 12 may process the digitized raw data to obtain physiological measurements, such as pulse rate, blood oxygen saturation, and/or a measurement of total hemoglobin. In step 108, the patient monitor 12 may display the physiological measurements on the display 16.

FIGS. 9 and 10 represent alternative systems for intercommunication between the medical sensor 14 and the electronic patient monitor 12. In particular, FIG. 9 illustrates a system employing the techniques described herein using an additional cable connector with memory or processing circuitry, and FIG. 10 illustrates a system employing the techniques described herein using wireless communication in place of the digital cable 26. Turning first to FIG. 9, a system 110 for intercommunication between the medical sensor 14 and the patient monitor 12 may include a digitizing cable 112 coupled to the sensor connector 22 of the analog cable 18. The digitizing cable 112 may include the sensor-side cable connector 24, which may be configured in the manners described above. Rather than include a monitor-side cable connector 28 with memory or processing circuitry, the digitizing cable may include a dumb connector 114 that may only transfer digital signals in the manner received from the sensor-side cable connector 24. Thus, the digitizing cable 112 may simply digitize analog raw data received from the medical sensor 14 into digital raw data.

In contrast, a smart connector 116 may include memory circuitry and/or processing circuitry for obtaining physiological measurements from digitized raw data. As such, the smart connector 116 may include substantially the same circuitry as the monitor-side cable connector 28, as illustrated in FIG. 3 or 7. The smart connector 116 may couple to the dumb connector 114 of the digitizing cable 112 using any suitable manner to supply power to and exchange digital communication with the digitizing cable 112. In general, the smart connector 116 may interconnect with the dumb connector 114 in substantially the same way as the monitor-side cable connector 28 with the monitor connector 30 in the system 10. The smart connector 116 may interconnect with the monitor connector 30 in much the same way. As such, the smart connector 116 may employ a digital communication interface such as a serial peripheral interface (SPI, a universal serial bus (USB) interface, a universal asynchronous receiver/transmitter (UART) interface, or an RS232 interface, or any other suitable communication link. In particular, the interface between the smart connector 116 and the monitor connector 30 may be a data link.

FIG. 10 illustrates a sensor-monitor intercommunication link system 118 for intercommunication between the medical sensor 14 and the patient monitor 12 that may include wireless communication circuitry. Functioning largely like the system 10, the system 118 may include sensor-monitor wireless communication link 120 in place of the sensor-monitor intercommunication cable 20. A sensor-side wireless adapter 122 may establish wireless communication 124 with a monitor-side wireless adapter 126 using any suitable protocol. By way of example, the protocol may include the IEEE 802.15.4 standard, and may employ, for example, the ZigBee, WirelessHART, or MiWi protocols. Additionally or alternatively, the protocol may include the Bluetooth standard or one or more of the IEEE 802.11 standards. In some embodiments, the wireless communication 124 may include optical communication, such as free space optics (FSO).

The sensor-side wireless adapter 122 and the monitor-side wireless adapter 126 may include substantially the same circuitry as the sensor-side cable connector 24 and the monitor-side cable connector 28, respectively, except that the digital communication interfaces 40 and 52 may be configured for wireless communication and may include one or more rechargeable or replaceable batteries. The monitor-side wireless adapter 126 may couple to the monitor connector 30 in the same manner as the monitor-side cable connector 28 or the smart connector 116. It should be understood that the wireless interface may, additionally or alternatively, form part of the monitor 12. With such embodiments, the external connector 30 may be omitted. Also, in some embodiments, the sensor 14 may employ a single microcontroller without connector 22, whereby the microcontroller may sample the data obtained by the sensor and may also provide the processing required for wireless communication.

Like the system 10 discussed above, the systems 110 of FIG. 9 and 118 of FIG. 10 may similarly enable rapid dispersion of improvements in sensor 14 processing techniques that may otherwise require an upgraded OEM module for the patient monitor 12. Thus, rather than supply a new OEM module, a vendor may supply a sensor-monitor intercommunication cable 20, a smart connector 116, or a monitor-side wireless adapter 126 with upgraded circuitry. The new sensor-monitor intercommunication cable 20, smart connector 116, or monitor-side wireless adapter 126 may be capable of processing digitized data to obtain physiological measurements or of providing such instructions to the patient monitor 12, as described above.

In certain embodiments of the systems 10, 110, or 118, the sensor-monitor intercommunication cable 20, smart connector 116, or monitor-side wireless adapter 126 may be upgradeable via software updates from a networked electronic patient monitor. FIG. 11 is a flowchart 128 illustrating one embodiment of a method for upgrading a sensor-monitor intercommunication cable 20, smart connector 116, or monitor-side wireless adapter 126. In a first step 130, software updates, such as firmware or driver updates, may be downloaded onto a networked electronic patient monitor 12. In step 132, the sensor-monitor intercommunication cable 20, smart connector 116, or monitor-side wireless adapter 126 may be attached to the electronic patient monitor 12. In step 134, the electronic patient monitor may upload the firmware or driver to the nonvolatile memory 62 of the sensor-monitor intercommunication cable 20, smart connector 116, or monitor-side wireless adapter 126. It should be understood that the software upgrades provided in the flowchart 128 may enable various additional or alternative methods for determining the physiological parameters from the digital raw data. Additionally or alternatively, the software upgrades may enable the sensor-monitor intercommunication cable 20, smart connector 116, or monitor-side wireless adapter 126 to send and/or receive messages in a particular medical messaging protocol. It should further be understood that the flowchart 128 may alternatively be carried out by connecting the sensor-monitor intercommunication cable 20, smart connector 116, or monitor-side wireless adapter 126 to a special- or general-purpose computer rather than the electronic patient monitor 12.

As noted above, the sensor-monitor intercommunication cable 20, smart connector 116, or monitor-side wireless adapter 126 may communicate with the electronic patient monitor 12 using a specific protocol, such as the Standard Host Interface Protocol (SHIP) or the Phillips Interface Protocol (PIP). The specific protocol may be selectable by a practitioner via, for example, the button or switch 25 or by programming the cable with particular firmware or drivers. Additionally or alternatively, the monitor 12, the sensor-monitor intercommunication cable 20, smart connector 116, or monitor-side wireless adapter 126 may automatically select the proper protocol for communication with the electronic patient monitor 12. FIGS. 12-17 are flowcharts representing embodiments of methods for automatically selecting such a protocol for use in the sensor-monitor intercommunication cable 20, smart connector 116, or monitor-side wireless adapter 126.

Specifically, FIG. 12 is a flowchart 136 representing an embodiment of a method for automatically selecting a protocol in the sensor-monitor intercommunication cable 20, smart connector 116, or monitor-side wireless adapter 126 based on an initialization message from the electronic patient monitor 12. In a first step 138, the monitor 12 may be initialized. During an initialization procedure, the monitor 12 may send one or more initialization messages to each of the sensors that may be coupled to the monitor 12 in step 140. After receiving the initialization messages in step 140, in step 142, the sensor-monitor intercommunication cable 20, smart connector 116, or monitor-side wireless adapter 126 may determine the protocol in which the initialization message is encoded. The determination of step 142 may involve, for example, a comparison of initialization messages of various protocols stored in the ROM 60 or the nonvolatile memory 62, or an analysis of the syntax or semantics of the initialization message. After the protocol of the monitor 12 has been determined in step 142, the sensor-monitor intercommunication cable 20, smart connector 116, or monitor-side wireless adapter 126 may store the determined protocol in the RAM 58 or the nonvolatile storage 62. Thereafter, the sensor-monitor intercommunication cable 20, smart connector 116, or monitor-side wireless adapter 126 may communicate with the electronic patient monitor 12 using a protocol that the electronic patient monitor understands.

Similarly, FIG. 13 is a flowchart 146 representing an embodiment of a method for automatically selecting a protocol in the sensor-monitor intercommunication cable 20, smart connector 116, or monitor-side wireless adapter 126 based on the response to messages sent using a variety of protocols. In a first step 148, the sensor-monitor intercommunication cable 20, smart connector 116, or monitor-side wireless adapter 126 may be connected to the electronic patient monitor 12. The sensor-monitor intercommunication cable 20, smart connector 116, or monitor-side wireless adapter 126 may transmit a test message in a first protocol in step 150. By way of example, the first protocol may be the Standard Host Interface Protocol (SHIP).

As illustrated by a decision block 152, if the electronic patient monitor 12 does not understand the first protocol, the electronic patient monitor 12 may not respond or may respond with an error message. If so, after a timing-out period, in step 154, the sensor-monitor intercommunication cable 20, smart connector 116, or monitor-side wireless adapter 126 may send a second test message in a second protocol. By way of example, the second protocol may be the Phillips Interface Protocol (PIP).

Returning to the decision block 152, if the electronic patient monitor 12 does understand the second protocol, the electronic patient monitor 12 may respond with a message other than an error message. If so, in step 156, the sensor-monitor intercommunication cable 20, smart connector 116, or monitor-side wireless adapter 126 may store the protocol that achieved a non-error message response from the monitor 12 in the RAM 58 or nonvolatile storage 62. On the other hand, if the electronic patient monitor 12 does not understand the second protocol, the sensor-monitor intercommunication cable 20, smart connector 116, or monitor-side wireless adapter 126 may continue to send test messages in various protocols, which may be preprogrammed in the ROM 60 or nonvolatile storage 62, until the electronic patient monitor 12 responds favorably.

The sensor-monitor intercommunication cable 20, smart connector 116, or monitor-side wireless adapter 126 may discern whether a response from the electronic patient monitor 12 is valid in any suitable manner. For example, the sensor-monitor intercommunication cable 20, smart connector 116, or monitor-side wireless adapter 126 may send test messages in every protocol preprogrammed in ROM 60 or nonvolatile storage 62 and store the responses from the monitor 12. If certain responses differ from other responses, and particularly if one response is different from all other responses, the sensor-monitor intercommunication cable 20, smart connector 116, or monitor-side wireless adapter 126 may determine that the other responses are error messages and the different response(s) is a normal response. Alternatively, the sensor-monitor intercommunication cable 20, smart connector 116, or monitor-side wireless adapter 126 may compare the responses as they arrive to stored error messages in the ROM 60 or nonvolatile storage 62 to determine what responses from the electronic patient monitor 12 are normal responses indicating that the monitor 12 understands the protocol of the test message and which responses are error messages indicating that the monitor 12 does not understand the protocol of the test message. In some embodiments, the sensor-monitor intercommunication cable 20 may send an intentionally errored message to the monitor 12. The protocol of the monitor 12 can be narrowed down based on whether the monitor 12 replies to errored messages and/or the format of the response. Certain protocols (e.g. SHIP) may have one or more SYNC byte(s) to start a message and cyclic redundancy cheek (CRC) for error checking, which may reduce ambiguity in determining whether a message from the monitor 12 is valid.

FIG. 14 is a flowchart 158 representing an embodiment of a method for automatically selecting a protocol in the sensor-monitor intercommunication cable 20, smart connector 116, or monitor-side wireless adapter 126 based on the response to messages sent using a variety of protocols. In a first step 160, the sensor-monitor intercommunication cable 20, smart connector 116, or monitor-side wireless adapter 126 may be connected to the electronic patient monitor 12. In step 162, the sensor-monitor intercommunication cable 20, smart connector 116, or monitor-side wireless adapter 126 may recall the most recently negotiated protocol, which may have been stored in non-volatile storage 62. The sensor-monitor intercommunication cable 20, smart connector 116, or monitor-side wireless adapter 126 may transmit a test message in the recalled protocol in step 164. Thereafter, decision block 166 and steps 168 and 170 may take place in substantially the same manner as decision block 152 and steps 154 and 156 of the flowchart 146 of FIG. 13.

FIG. 15 is a flowchart 172 representing an embodiment of a method for automatically selecting a protocol in the sensor-monitor intercommunication cable 20, smart connector 116, or monitor-side wireless adapter 126 based on a configuration message from the patient monitor 12. In a first step 174, the sensor-monitor intercommunication cable 20, smart connector 116, or monitor-side wireless adapter 126 may be connected to the electronic patient monitor 12. In step 176, the patient monitor 12 may provide a configuration message. The configuration message may be provided in a format that was previously agreed upon by many or all manufacturers of patient monitors 12. The message may indicate various information regarding the operation of the patient monitor 12, including the communication protocol employed by the patient monitor 12. In step 178, the sensor-monitor intercommunication cable 20, smart connector 116, or monitor-side wireless adapter 126 may store the protocol indicated by the configuration message from the monitor 12 in the RAM 58 or nonvolatile storage 62.

FIG. 16 is a flowchart 180 representing an embodiment of a method for automatically selecting a protocol in the sensor-monitor intercommunication cable 20, smart connector 116, or monitor-side wireless adapter 126 based on a connector 18 pin identification code from the patient monitor 12. In a first step 182, the sensor monitor intercommunication cable 20, smart connector 116, or monitor-side wireless adapter 126 may be connected to the electronic patient monitor 12. In some embodiments, certain pins of the connecter 18 of the patient monitor 12 may be connected to power or ground, or to specific resistors or voltages, which may uniquely identify the type of the patient monitor 12 or the protocol employed by the patient monitor 12. For such embodiments, in step 184, sensor-monitor intercommunication cable 20, smart connector 116, or monitor-side wireless adapter 126 may detect such a connector 18 pin identification code that may identify the communication protocol employed by the patient monitor 12. In step 186, the sensor-monitor intercommunication cable 20, smart connector 116, or monitor-side wireless adapter 126 may store the protocol indicated by the connector 18 pin identification code from the monitor 12 in the RAM 58 or nonvolatile storage 62.

FIG. 17 is a flowchart 188 representing an embodiment of a method for automatically selecting a protocol in the sensor-monitor intercommunication cable 20, smart connector 116, or monitor-side wireless adapter 126 based on a USB device enumeration process. As noted above, in some embodiments, the sensor-monitor intercommunication cable 20, smart connector 116, or monitor-side wireless adapter 126 may be connected to the electronic patient monitor 12 via a USB connection. Such embodiments, as noted step 190, may be attached to the patient monitor 12. A USB device enumeration process may ensue. In step 192, based on information retrieved from the patient monitor 12 during the USB device enumeration process, the type of patient monitor 12 may be identified. With knowledge of the type of the patient monitor 12, the sensor-monitor intercommunication cable 20, smart connector 116, or monitor-side wireless adapter 126 may identify the protocol employed by such type of patient monitor 12. Thus, in step 186, the sensor-monitor intercommunication cable 20, smart connector 116, or monitor-side wireless adapter 126 may store the protocol indicated by the USB device enumeration process into the RAM 58 or nonvolatile storage 62.

While many of the methods for determining the communication protocol generally have been described as taking place in the sensor-monitor intercommunication cable 20, smart connector 116, or monitor-side wireless adapter 126, it should be understood that such methods may, additionally or alternatively, take place in the patient monitor 12. That is, the patient monitor 12 may perform those actions ascribed to the sensor-monitor intercommunication cable 20, smart connector 116, or monitor-side wireless adapter 126, to determine which communication protocol to employ.

In alternative embodiments, the sensor-monitor intercommunication cable 20, smart connector 116, or monitor-side wireless adapter 126 may communicate with the electronic patient monitor 12 in other ways. For example, rather than communicate using a single protocol, the sensor-monitor intercommunication cable 20, smart connector 116, or monitor-side wireless adapter 126 may communicate a single message using several protocols, and the electronic patient monitor 12 may disregard messages not encoded in the protocol it understands. Additionally or alternatively, the sensor-monitor intercommunication cable 20, smart connector 116, or monitor-side wireless adapter 126 may output information in a universal protocol not specific to a particular vendor, or may output raw information using a protocol such as serial peripheral interface (SPI) or universal serial bus (USB).

While the embodiments set forth in the present disclosure may be susceptible to various modifications and alternative forms, specific embodiments have been shown by way of example in the drawings and have been described in detail herein. However, it should be understood that the disclosure is not intended to be limited to the particular forms disclosed. The disclosure is to cover all modifications, equivalents, and alternatives falling within the spirit and scope of the disclosure as defined by the following appended claims. 

1-24. (canceled)
 25. An oximetry assembly comprising: a cable assembly including a proximal end and a distal end; an oximetry sensor located at the distal end of the cable assembly, the oximetry sensor configured to attach to a finger and comprising at least one emitter and at least one detector, the at least one emitter configured to transmit light at one or more wavelengths into tissue, the at least one detector configured to receive the light after the light passes through or is reflected by the tissue and to generate oximetry data based on the light received; a connector located at the proximal end of the cable assembly; and a processor housed within the cable assembly, wherein the processor is programmed to communicate using at least a first protocol, and wherein the processor is configured to use at least the first protocol to transmit the oximetry data.
 26. The oximetry assembly of claim 25, wherein the processor is configured to determine when the oximetry data is encoded in at least a second protocol, and wherein the processor is configured to translate the oximetry data from at least the second protocol to at least the first protocol.
 27. The oximetry assembly of claim 25, wherein the processor is configured to receive the oximetry data as raw oximetry data from the oximetry sensor, wherein the processor of the cable assembly is configured to digitize the raw oximetry data into digital oximetry data.
 28. The oximetry assembly of claim 25, wherein the cable assembly further comprises sensor-monitor intercommunication circuitry storing instructions for obtaining oximetry measurements from raw oximetry data.
 29. The oximetry assembly of claim 25, wherein the oximetry sensor is controlled by the processor.
 30. The oximetry assembly of claim 25, wherein the cable assembly includes a sensor-monitor intercommunication cable having a sensor-side cable connector and a monitor-side cable connector.
 31. The oximetry assembly of claim 25, wherein the oximetry data includes blood oxygen saturation and pulse rate.
 32. The oximetry assembly of claim 25, wherein the processor comprises a microprocessor and software configured to perform one or both of measurements or calculations to determine oxygen saturation and pulse rate based on the oximetry data received from the oximetry sensor.
 33. The oximetry assembly of claim 25, wherein the processor is configured to download software updates from a remote source.
 34. An oximetry assembly configured to be connected to a device including a display that is configured to display physiological measurements based on oximetry data, the oximetry assembly comprising: a cable assembly including a proximal end and a distal end; an oximetry sensor located at the distal end of the cable assembly, the oximetry sensor configured to attach to a finger and comprising at least one emitter and at least one detector, the at least one emitter configured to transmit light at one or more wavelengths into tissue, the at least one detector configured to receive the light after the light passes through or is reflected by the tissue and to generate oximetry data based on the light received; a connector located at the proximal end of the cable assembly, the connector configured to removably connect the oximetry sensor to the device and allow communication with the device through a data communication link; and a processor housed within the cable assembly, wherein the processor is programmed to communicate with the device using at least one device protocol of the devic, and wherein the processor is configured to use the at least one device protocol to transmit the oximetry data to the device.
 35. The oximetry assembly of claim 34, wherein the processor is configured to determine when the oximetry data is encoded in at least one sensor protocol, and wherein the processor is configured to translate the oximetry data from the at least one sensor protocol to the at least one device protocol.
 36. The oximetry assembly of claim 34, wherein the processor is configured to receive the oximetry data as raw oximetry data from the oximetry sensor, wherein the processor is configured to digitize the raw oximetry data into digital oximetry data and provide the digital oximetry data to the device for display of the information based on the digital oximetry data.
 37. The oximetry assembly of claim 34, further comprising sensor-monitor intercommunication circuitry within the cable assembly, wherein the sensor-monitor intercommunication circuitry stores instructions for obtaining oximetry measurements from raw oximetry data, and wherein the processor is configured to provide the instructions to the device.
 38. The oximetry assembly of claim 34, wherein the oximetry sensor is controlled by the processor.
 39. The oximetry assembly of claim 34, wherein the cable assembly includes a sensor-monitor intercommunication cable having a sensor-side cable connector and a monitor-side cable connector.
 40. The oximetry assembly of claim 34, wherein the oximetry data includes blood oxygen saturation and pulse rate.
 41. The oximetry assembly of claim 34, wherein the processor comprises a microprocessor and software configured to perform one or both of measurements or calculations to determine oxygen saturation and pulse rate based on the oximetry data received from the oximetry sensor.
 42. The oximetry assembly of claim 34, wherein the data communication link includes one of a serial peripheral interface (SPI), a universal serial bus (USB) interface, a universal asynchronous reciver/transmitter (UART), a two wire interface (TWI), or an RS232 interface.
 43. The oximetry assembly of claim 34, wherein the processor is configured to download software updates from a remote source.
 44. An oximetry system comprising: a device including a display that is configured to display physiological measurements based on oximetry data, wherein the device is configured to communicate using at least one device protocol; and an oximetry assembly configured to removably connect to the device, the oximetry assembly comprising: a cable assembly including a proximal end and a distal end; an oximetry sensor located at the distal end of the cable assembly, the oximetry sensor configured to attach to a finger and comprising at least one emitter and at least one detector, the at least one emitter is configured to transmit light at one or more wavelengths into tissue, the at least one detector configured to receive the light after the light passes through or is reflected by the tissue and to generate the oximetry data based on the light received; a connector located at the proximal end of the cable assembly, the connector configured to removably connect the oximetry sensor to the device and allow communication with the device through a data communication link; and a processor housed within the cable assembly, wherein the processor is configured to communicate with the device using the at least one device protocol, wherein the processor is programmed to communicate with the device using the at least one device protocol, wherein the processor is configured to use the at least one device protocol to transmit the oximetry data to the device.
 45. The oximetry system of claim 44, wherein the processor is configured to determine when the oximetry data is encoded in at least one sensor protocol, and wherein the processor is configured to translate the oximetry data from the at least one sensor protocol to the at least one device protocol.
 46. The oximetry system of claim 44, wherein the processor is configured to receive the oximetry data as raw oximetry data from the oximetry sensor, wherein the processor is configured to digitize the raw oximetry data into digital oximetry data and provide the digital oximetry data to the device, and wherein the device is configured to display the information based on the digital oximetry data on the display.
 47. The oximetry system of claim 44, wherein the device is devoid of an oximetry processor, wherein the device is not specifically configured to extract oximetry measurements, and wherein the device is unable to process data into oximetry measurements without the oximetry assembly.
 48. The oximetry system of claim 44, wherein the device is manufactured by a first manufacturer, and wherein the oximetry assembly is manufactured by a second manufacturer that differs from the first manufacturer.
 49. The oximetry system of claim 44, wherein one or both of the processor or the device is configured to download software updates from a remote source.
 50. The oximetry system of claim 44, wherein the at least one device protocol includes one of a Standard Host Interface Protocol (SHIP) or a Phillips Interface Protocol (PIP).
 51. The oximetry system of claim 44, wherein the device comprises an oximetry monitor.
 52. The oximetry system of claim 44, wherein the device is devoid of an oximetry processor.
 53. The oximetry system of claim 44, wherein the device is not specifically configured to extract oximetry measurements.
 54. The oximetry system of claim 44, wherein the device is unable to process data into oximetry measurements without the oximetry assembly. 